Welcome Guest, you are in: <root>T4 Admin GuideT4 AndroidT4 APIT4 API 40T4 API FIXT4 Chart Scripting GuideT4 Client FAQT4 Client GuideT4 iOST4 MobileT4 VideosT4 WebTrader • Login

Page History: Logon

Compare Page Revisions

152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Current 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

« Older Revision - Back to Page History - Newer Revision »

Page Revision: 2012/08/31 18:14

Session Initiation

Upon an established TCP connection, the T4 FIX API basic requirement is to have the initiator and acceptor start sequence numbers from 1.

Drop of a physical (TCP socket) connection will result in the end of a FIX session. Upon reconnection, a new FIX session will be started with a sequence number of 1 (for the API User). Likewise, the T4 API server will respond with messages starting with a sequence number of 1.

Authentication Requirements

Message Dictionary Descriptions

ag !Field Name !Req'd !Comments
|Standard Header |Y |MsgType = A
8 |EncryptMethod |Y |(Always unencrypted)
5 |RawDataLength |N |Required for some authentication methods
6 |RawData |N |Required for some authentication methods
41 |ResetSeqNumFlag |N |Indicates both sides of a FIX session should reset sequence numbers
89 |NextExpectedMsgSeqNum |N |Optional, alternative via counterparty bi-lateral agreement message gap detection and recovery approach
83 |MaxMessageSize |N |Can be used to specify the maximum number of bytes supported for messages received

Trade how you want, where you want

support@ctsfutures.com (312) 939 0164

2 Pierce Pl, Suite 200, Itasca, IL 60143

© 2009-2023 Cunningham Trading Systems LLC All rights reserved.